Skip to content

api: add maxRequestHeaderLimit to ClientTrafficPolicy - #9623

Draft
hsubramanianaks wants to merge 1 commit into
envoyproxy:mainfrom
hsubramanianaks:feat/ctp-max-request-header-limit
Draft

api: add maxRequestHeaderLimit to ClientTrafficPolicy#9623
hsubramanianaks wants to merge 1 commit into
envoyproxy:mainfrom
hsubramanianaks:feat/ctp-max-request-header-limit

Conversation

@hsubramanianaks

Copy link
Copy Markdown

Adds headers.maxRequestHeaderLimit to ClientTrafficPolicy, mapping to Envoy's HTTP connection manager max_request_headers_kb setting. The value is a resource.Quantity rounded up to the nearest KiB, validated to be at least 1Ki and at most 8192Ki (Envoy's maximum). Requests whose headers exceed the limit receive a 431 response.

Scoped to the max-request-header field only (host normalization landed separately in #9115) and named with the *Limit suffix per maintainer feedback on #8825.

Fixes #5368

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #


PR Checklist

  • Authorship & ownership: Coding agents / AI assistants are welcome, but I have reviewed every change, understand how and why it works, can explain and maintain it, and take full responsibility for this PR. I have not submitted generated output I do not understand.
  • DCO: All commits are signed off (git commit -s). See DCO: Sign your work.
  • API agreed first: If this PR contains API changes (changes under /api), the API was discussed and agreed before the implementation. The API change can be in a separate PR, or in the same PR, but the API must be agreed before implementation. N/A if this PR does not contain API changes.
  • Required checks pass: make generate gen-check, make lint, and the unit-test/coverage build pass. (Flaky e2e failures are not considered breakages, but gen-check, lint, and coverage MUST pass.)
  • Tests added/updated: New/changed code is covered by appropriate tests. N/A if this PR does not contain code changes.
  • Docs: User-facing changes update the docs, either in this PR or a follow-up PR. N/A if this PR does not contain user-facing changes.
  • Release notes: For any non-trivial change, added a release-note fragment under release-notes/current/<section>/<pr-number>-<slug>.md (see release-notes/current/README.md for sections and naming). N/A if this PR does not contain non-trivial changes.
  • Generated files committed: Ran make gen-check and committed the result if API/helm charts/modules changed.
  • Scope & compatibility: The PR is reasonably scoped (no unrelated changes) and preserves backward compatibility, or any breaking change is called out above and documented in release-notes/current/breaking_changes/.
  • Codex review: Requested a Codex review and addressed all of its comments.
  • Copilot review: Requested a Copilot review and addressed all of its comments.

Adds headers.maxRequestHeaderLimit to ClientTrafficPolicy, mapping to Envoy's HTTP connection manager max_request_headers_kb setting. The value is a resource.Quantity rounded up to the nearest KiB, validated to be at least 1Ki and at most 8192Ki (Envoy's maximum). Requests whose headers exceed the limit receive a 431 response.

Scoped to the max-request-header field only (host normalization landed separately in envoyproxy#9115) and named with the *Limit suffix per maintainer feedback on envoyproxy#8825.

Fixes envoyproxy#5368

Signed-off-by: Hariharan Subramanian <hsubramanian@microsoft.com>
@netlify

netlify Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploy Preview for cerulean-figolla-1f9435 ready!

Name Link
🔨 Latest commit d6efaf6
🔍 Latest deploy log https://app.netlify.com/projects/cerulean-figolla-1f9435/deploys/6a6bf6a0bea2160008d553fa
😎 Deploy Preview https://deploy-preview-9623--cerulean-figolla-1f9435.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for max request header size

1 participant